﻿using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;

namespace MetaCollection.ContentService.Http
{
	/// <summary>
	/// 1xx Informational
	/// -------------------------------------
	/// Request received, continuing process.
	/// This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers,
	/// and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx
	/// response to an HTTP/1.0 client except under experimental conditions.
	/// </summary>
	public enum InfoStatus
	{
		None = 0,
		/// <summary>
		/// This means that the server has received the request headers, and that the client should proceed to send the
		/// request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the
		/// request body is large, sending it to a server when a request has already been rejected based upon inappropriate
		/// headers is inefficient. To have a server check if the request could be accepted based on the request's headers
		/// alone, a client must send Expect: 100-continue as a header in its initial request (see RFC 2616 §14.20 – Expect
		/// header) and check if a 100 Continue status code is received in response before continuing (or receive 417
		/// Expectation Failed and not continue).
		/// </summary>
		Continue = 100,
		/// <summary>
		/// This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.
		/// </summary>
		SwitchingProtocols = 101,
		/// <summary>
		/// (WebDAV) (RFC 2518 )
		/// </summary>
		Processing = 102
	}
}
